Skip to content

Conversation

BigLep
Copy link
Member

@BigLep BigLep commented Sep 26, 2025

Added documentation for ChainGetFinalizedTipSet API. This is a copy/paste from https://github.com/filecoin-project/lotus/blob/master/documentation/en/api-methods-v1-stable.md#ChainGetFinalizedTipSet

@BigLep BigLep requested a review from Copilot September 26, 2025 01:09
@BigLep BigLep added this to FilOz Sep 26, 2025
@github-project-automation github-project-automation bot moved this to 📌 Triage in FilOz Sep 26, 2025
Copy link

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR adds documentation for the ChainGetFinalizedTipSet JSON-RPC API method, providing comprehensive details about its functionality, permissions, inputs, and response format. The documentation explains that this method returns the latest finalized tipset using F3 consensus or falls back to Expected Consensus finality.

  • Added complete API documentation including method description, permissions, and response schema
  • Included detailed JSON response example showing the structure of a finalized tipset

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

This is the tipset at the end of the last finalized round and can be used
for follow-up querying of the chain state with the assurance that the
state will not change.
If F3 is operational and finalizing in this node. If not, it will fall back
Copy link
Preview

Copilot AI Sep 26, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The sentence on line 299 is incomplete. It should read 'This method returns the finalized tipset if F3 is operational and finalizing in this node.'

Suggested change
If F3 is operational and finalizing in this node. If not, it will fall back
This method returns the finalized tipset if F3 is operational and finalizing in this node. If not, it will fall back

Copilot uses AI. Check for mistakes.

@BigLep
Copy link
Member Author

BigLep commented Sep 26, 2025

I thought json-rpc API documentation in the repo was automated but then I didn't see where that was done...

@rjan90 or @lanzafame : let me know if I should do this differently.

@lanzafame
Copy link
Collaborator

I don't think it occurs within this repo. @rjan90 any idea?

@rjan90
Copy link
Contributor

rjan90 commented Sep 30, 2025

My knowledge of how the Filecoin documentation is structure is limited, but from my understanding I do not think either the Lotus or Filecoin docs sites has had automated API documentation.

@rjan90
Copy link
Contributor

rjan90 commented Sep 30, 2025

@lanzafame change here looks good to me.

@BigLep
Copy link
Member Author

BigLep commented Sep 30, 2025

I thought json-rpc API documentation in the repo was automated but then I didn't see where that was done...

I'm remembering now. I believe there is automation for filecoin-projects/lotus-docs to pull in whatever is done in this repo.

Ideally these RPC docs would get autogenerated by code or other assets in Lotus, but I don't think anyone has the bandwidth for that currently.

As a result, I propose we just go the manual route for now so that F3 blog entries, etc. can link to an official API doc.

@lanzafame : are you ok to merge? I see there are broken links unrelated to my change.

@BigLep BigLep moved this from 📌 Triage to 🔎 Awaiting Review in FilOz Oct 5, 2025
@BigLep
Copy link
Member Author

BigLep commented Oct 5, 2025

@lanzafame : I'm hoping to publish a f3-related blog post soon and I'd like to like to this API definition. Are you ok to merge?

@BigLep
Copy link
Member Author

BigLep commented Oct 6, 2025

@lanzafame : I'll plan to merge this 2025-10-07 Pacific time if I don't hear anything otherwise.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 🔎 Awaiting Review
Development

Successfully merging this pull request may close these issues.

3 participants